home *** CD-ROM | disk | FTP | other *** search
-
-
-
- aaaacccccccceeeessssssss((((2222)))) aaaacccccccceeeessssssss((((2222))))
-
-
-
- NNNNAAAAMMMMEEEE
- _aaaa_cccc_cccc_eeee_ssss_ssss - determine accessibility of a file
-
- SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
- _####_iiii_nnnn_cccc_llll_uuuu_dddd_eeee _<<<<_uuuu_nnnn_iiii_ssss_tttt_dddd_...._hhhh_>>>>
-
- _iiii_nnnn_tttt _aaaa_cccc_cccc_eeee_ssss_ssss_((((_cccc_oooo_nnnn_ssss_tttt _cccc_hhhh_aaaa_rrrr _****_pppp_aaaa_tttt_hhhh_,,,, _iiii_nnnn_tttt _aaaa_mmmm_oooo_dddd_eeee_))))_;;;;
-
- DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
- _p_a_t_h points to a path name naming a file. _aaaa_cccc_cccc_eeee_ssss_ssss checks the named file
- for accessibility according to the bit pattern contained in _a_m_o_d_e, using
- the real user ID in place of the effective user ID and the real group ID
- in place of the effective group ID. The bit pattern contained in _a_m_o_d_e
- is constructed by an OR of the following constants (defined in
- <_uuuu_nnnn_iiii_ssss_tttt_dddd_...._hhhh>):
-
- _RRRR______OOOO_KKKK test for read permission
- _WWWW______OOOO_KKKK test for write permission
- _XXXX______OOOO_KKKK test for execute (search) permission
- _FFFF______OOOO_KKKK test for existence of file
- _EEEE_XXXX______OOOO_KKKK test for regular, executable file
- _EEEE_FFFF_FFFF______OOOO_NNNN_LLLL_YYYY______OOOO_KKKK test using effective IDs
-
- Note that successful checking of the _EEEE_XXXX______OOOO_KKKK file does not imply that the
- _eeee_xxxx_eeee_cccc(2) system call will succeed on the file named by _p_a_t_h, since the
- check succeeds if at least one execute bit is set; there are also
- additional checks made for execute permission by _eeee_xxxx_eeee_cccc.
-
- Access to the file is denied if one or more of the following are true:
-
- _EEEE_AAAA_CCCC_CCCC_EEEE_SSSS Search permission is denied on a component of the
- path prefix.
-
- _EEEE_AAAA_CCCC_CCCC_EEEE_SSSS Access permission is denied.
-
- _EEEE_AAAA_CCCC_CCCC_EEEE_SSSS The file is not a regular file.
-
- _EEEE_FFFF_AAAA_UUUU_LLLL_TTTT _p_a_t_h points outside the allocated address space for
- the process.
-
- _EEEE_IIII_NNNN_TTTT_RRRR A signal was caught during the _aaaa_cccc_cccc_eeee_ssss_ssss system call.
-
- _EEEE_IIII_NNNN_VVVV_AAAA_LLLL _a_m_o_d_e is invalid.
-
- _EEEE_LLLL_OOOO_OOOO_PPPP Too many symbolic links were encountered in
- translating _p_a_t_h.
-
- _EEEE_MMMM_UUUU_LLLL_TTTT_IIII_HHHH_OOOO_PPPP Components of _p_a_t_h require hopping to multiple remote
- machines.
-
-
-
-
-
-
- PPPPaaaaggggeeee 1111
-
-
-
-
-
-
- aaaacccccccceeeessssssss((((2222)))) aaaacccccccceeeessssssss((((2222))))
-
-
-
- _EEEE_NNNN_AAAA_MMMM_EEEE_TTTT_OOOO_OOOO_LLLL_OOOO_NNNN_GGGG The length of the _p_a_t_h argument exceeds {_PPPP_AAAA_TTTT_HHHH______MMMM_AAAA_XXXX},
- or the length of a _p_a_t_h component exceeds {_NNNN_AAAA_MMMM_EEEE______MMMM_AAAA_XXXX}
- while ______PPPP_OOOO_SSSS_IIII_XXXX______NNNN_OOOO______TTTT_RRRR_UUUU_NNNN_CCCC is in effect.
-
- _EEEE_NNNN_OOOO_TTTT_DDDD_IIII_RRRR A component of the path prefix is not a directory.
-
- _EEEE_NNNN_OOOO_EEEE_NNNN_TTTT Read, write, or execute (search) permission is
- requested for a null path name.
-
- _EEEE_NNNN_OOOO_EEEE_NNNN_TTTT The named file does not exist.
-
- _EEEE_NNNN_OOOO_LLLL_IIII_NNNN_KKKK _p_a_t_h points to a remote machine and the link to that
- machine is no longer active.
-
- _EEEE_TTTT_IIII_MMMM_EEEE_DDDD_OOOO_UUUU_TTTT The named file is located on a remote file system
- which is not available [see _iiii_nnnn_tttt_rrrr_oooo(2)].
-
- _EEEE_RRRR_OOOO_FFFF_SSSS Write access is requested for a file on a read-only
- file system.
-
- SSSSEEEEEEEE AAAALLLLSSSSOOOO
- _cccc_hhhh_mmmm_oooo_dddd(2), _ssss_tttt_aaaa_tttt(2)
- ``File Access Permission'' in _iiii_nnnn_tttt_rrrr_oooo(2)
-
- DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
- If the requested access is permitted, a value of 0 is returned.
- Otherwise, a value of -1 is returned and _eeee_rrrr_rrrr_nnnn_oooo is set to indicate the
- error.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PPPPaaaaggggeeee 2222
-
-
-
-